Add VSCode extension for BSP server log streaming #113
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joshua-arnold
force-pushed
the
josh/vscode-extension
branch
from
ed74a0c to
751b1e0
Compare
joshua-arnold
changed the title
Introduces a TypeScript-based VSCode extension that integrates with the SourceKit Bazel BSP server. Includes basic extension scaffolding, logger utility, and build configuration.
joshua-arnold
force-pushed
the
josh/vscode-extension
branch
from
8bd4e0c to
65dfa7c
Compare
Member
|
Thanks @joshua-arnold! I'll give this a deeper look over the following days! |
Contributor
|
Thanks! No problem also if we want to go in another direction, just wanted to propose to get the ball rolling as I feel like the extension would be useful for eventually auto generating launch tasks etc, test running integration, + custom logic for detecting when new build files are added / modified in the work space etc. |
rockbruno
reviewed
Jan 10, 2026
Sources/SourceKitBazelBSP/RequestHandlers/BuildTargets/BazelTargetStore.swift
Outdated
Show resolved
Hide resolved
joshua-arnold
force-pushed
the
josh/vscode-extension
branch
2 times, most recently
from
82e419b to
41b5f5f
Compare
joshua-arnold
force-pushed
the
josh/vscode-extension
branch
from
41b5f5f to
de9853e
Compare
Contributor
Author
|
@rockbruno updated! The extension should be super bare-bones now, ready to be built on top of. I also added some basic CI steps that ensure it will compile without warnings. |
rockbruno
approved these changes
Jan 11, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a companion VSCode extension that streams logs from the SourceKit Bazel BSP server directly into a VSCode output channel, making it easier to monitor and debug BSP server activity without leaving the editor.
Motivation
At the moment, this extension only outputs important logs (errors) to VSCode tab. This will make it easy for people to identify errors instead of needing to setup a log stream and parse the large output.
Furthermore, we will be able to log other important warnings & information when needed.
Moving forward, hopefully we can start to support the remaining functionality in this extension:
Changes
New VSCode extension (
vscode-extension/)log streamcommandcom.spotify.sourcekit-bazel-bsp) and category (extension)New extension logger (
Sources/SourceKitBazelBSP/SharedUtils/Logger.swift)extensionLoggerfor user-facing messages intended to be shown in the VSCode extensionCI updates (
.github/workflows/ci.yaml)Test plan
Tested the extension in the example project: